Data files synchronization with cloud storage service

ABSTRACT

A method for synchronizing data files between a client device and a cloud storage service (CSS). The method comprises marking each data file that has been changed since a last synchronization between the client device and the CSS; dividing each marked data file into a plurality of blocks; assigning each block with a unique code; determining, based on the assigned the unique codes, a set of modified blocks from among the plurality of blocks; and synchronizing the set of modified blocks such that the CSS and the client device include a consistent version of each data file that has changed.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation application of U.S. patent application Ser. No. 15/463,433, filed on Mar. 20, 2017, now U.S. Pat. No. 10,574,753, which is a continuation of U.S. patent application Ser. No. 12/641,559, filed on Dec. 18, 2009, now U.S. Pat. No. 9,614,924, which claims the benefit of U.S. Provisional Application No. 61/140,071 filed on Dec. 22, 2008, the contents of which are herein incorporated by reference

TECHNICAL FIELD

The disclosure relates generally to storage networks, and more particularly to integrated local and cloud storage services.

BACKGROUND

The demand for storage has been rapidly increasing, as the amount of data such as digital media stored by users grows, so does their need to store digital media reliably over extended periods of time. Traditional, backup solutions periodically copy data to, for example, backup tapes, compact discs (CDs), or other local storage media. However, such solutions are not optimal as the backup media is stored in a single location and media used for backup are prone to failure.

Other solutions include storing data files on a local hard-drive of a personal computer (PC) and synchronizing the data remotely using hosted storage services. Having a remote backup ensures data is stored in multiple locations, and be protected local disasters, such as fires or floods. However, such solutions require installation of special client software on each individual PC, which is prone to software incompatibilities, lack of central control, and high deployment cost.

Commercially available services referred to as cloud storage services provide mass storage through a web service interface available through the Internet. FIG. 1 illustrates a storage system 100 designed to provide cloud storage services. The system 100 includes a distributed array of geographically distributed data centers 110-1 to 110-M connected to a plurality of clients 120-1 to 120-N through a wide area network (WAN) 130.

A data center 110 typically consists of servers and mass storage facilitating cloud storage services to the clients 120. Such services enable applications including, for example, backup and restore of data, data migration, data sharing, data collaboration, and so on. Cloud storage services are accessible from anywhere in the world. To this end, each client 120 implements a web services interface designed to at least synchronize data with the data centers 110. Applications enabled by the cloud storage services are not aware of the specifics of the services and the underlying data synchronization operations. The disadvantage of commercially available cloud storage services is that such services do not implement standard file sharing protocols (e.g., common internet file system (CIFS) or network file system (NFS)). Furthermore, accessing files stored in the cloud storage is typically slower than accessing files stored in local storage devices.

A network-attached storage (NAS) device is a self-contained appliance connected to a network with a primary purpose of supplying file-based data storage services to clients on the network. Specifically, a NAS device provides the functionality of data storage, file-based operations (e.g., read, write, delete, modify, etc.), and the management of these functionalities. However, commercially available NAS devices do not operate in conjunction with cloud storage services. Therefore, organizations and businesses utilizing NAS devices to store and manage their data cannot benefit from mass storage and applications of cloud storage services.

It would be therefore advantageous to provide a solution for integrating NAS devices with cloud storage services.

SUMMARY

Certain embodiments disclosed herein include a method for synchronizing data files between a client device and a cloud storage service (CSS). The method comprises marking each data file that has been changed since a last synchronization between the client device and the CSS; dividing each marked data file into a plurality of blocks; assigning each block with a unique code; determining, based on the assigned the unique codes, a set of modified blocks from among the plurality of blocks; and synchronizing the set of modified blocks such that the CSS and the client device include a consistent version of each data file that has changed.

Certain embodiments disclosed herein also include method for storing, in a cloud storage service (CSS), data files that are locally stored in a client device. The method comprises dividing each data file into a plurality of blocks; assigning each block of the plurality of blocks with a unique code; determining, based on the unique codes, at least one block that is not stored in the CSS; and transmitting the determined at least one block to the CSS to be stored in the CSS, thereby maintaining at least one consistent version of each data file.

Certain embodiments disclosed herein also include a system for storing data files in a cloud storage service (CSS). The system comprises storage configure to store a plurality of data files; a processor; and a memory, the memory containing instructions that, when executed by the processor, configure the system to: for each data file of the plurality of data files locally stored in the storage: divide the data file into a plurality of blocks; assign each block of the plurality of blocks with a unique code; determine, based on the unique codes, at least one block that is not stored in the CSS; and transmit the at least one block to the CSS to be stored in the CSS, thereby maintaining at least one consistent version of the data file.

BRIEF DESCRIPTION OF THE DRAWINGS

The subject matter disclosed herein is particularly pointed out and distinctly claimed in the claims at the conclusion of the specification. The foregoing and other features and advantages of the will be apparent from the following detailed description taken in conjunction with the accompanying drawings.

FIG. 1 is a diagram of a storage network system.

FIG. 2 is a storage network system useful in describing the various disclosed embodiments.

FIG. 3 is a cloud storage service (CSS) constructed in accordance with an embodiment.

FIG. 4 is an exemplary and non-limiting block diagram of a device constructed in accordance with an embodiment.

FIG. 5 is an exemplary flowchart describing the process for data synchronization implemented in accordance with an embodiment.

FIG. 6 is an exemplary and non-limiting block diagram of a cloud connector implemented in accordance with an embodiment.

DETAILED DESCRIPTION

It is important to note that the embodiments disclosed are only examples of the many advantageous uses of the innovative teachings herein. In general, statements made in the specification of the present disclosure do not necessarily limit any of the various claimed embodiments. Moreover, some statements may apply to some inventive features but not to others. In general, unless otherwise indicated, singular elements may be in plural and vice versa with no loss of generality. In the drawings, like numerals refer to like parts through several views.

FIG. 2 shows an exemplary and non-limiting diagram of a storage network system 200 utilized to describe some of the disclosed embodiments. The system 200 includes clients 210-1 to 210-N (generally referred to as client or clients 210) connected to a device 220 through a local area network (LAN) 230 which may be either a wireless or wired network. The clients 210 can perform file-based operations on the device 220 by using any type of a file sharing protocol including, but not limited to, a network file system (NFS), a common internet file system (CIFS), and the like. In addition, the device 220 is connected to data centers 260-1 to 260-M through a network 250 which may be the Internet or a wide area network (WAN). The data centers 260 may be geographically distributed and implement a cloud storage service (CSS) 240 constructed in accordance with an embodiment.

As illustrated in FIG. 3 the CSS 240 consists of a plurality of cloud connectors 310 that facilitate connections between the device 220 and storage devices 320-1 to 320-P (e.g., disk drives and/or SAN/NAS devices) as well as connections to third parties cloud storage providers 330-1 to 330-S (e.g., Amazon Web Services, Nirvanix, etc.). The cloud connectors 310 operate in parallel to enable load balancing and to avoid a single point of failure. In one embodiment, the web portal 340 is also provided to enable users to perform at least file-based operations on files stored in the CSS 240 using a web-base interface. In accordance with one embodiment local storage devices 320-1 to 320-P are administratively organized in device groups (DGs), each DG contains one or more devices, and when block encryption is used, DGs share the same block encryption key.

According to certain embodiments, in order to allow transparent access from clients 210 to files stored in the CSS 240, the device 220 provides a shared network folder (hereinafter the “virtual cloud drive” (VCD)). The VCD exposes files that are stored at the CSS 240. When a client 210 tries to access a specific byte range from a VCD of the device 220 that is mapped to the CSS 240, the device 220 transparently contacts the CSS 240 and requests the blocks including the requested byte range on behalf of the client 210. The blocks are then reassembled, decrypted and decompressed as needed, to recover the original byte range. The reconstructed byte range is then returned to the client 210. To the client 210, the file appears to be stored locally on the device 220. The device 220 may cache recently and/or frequently accessed data blocks in the memory 460 or and/or the storage 450. Such blocks can be returned directly from the cache instead of from the CSS 240.

FIG. 4 shows an exemplary and non-limiting block diagram of the device 220 constructed in accordance with an embodiment of the invention. The device 220 comprises a processor 410, network controllers 420-1 and 420-2 for interfacing with at least the LAN 230 and network 250, a plurality of storage controllers 430 for controlling storage devices 450 attached to the device 220, and non-volatile memory 460 for at least storing settings and configuration parameters required for the proper operation of the device 220. The memory 460 may be utilized to cache data transferred between the storage devices 450 and CSS 240. The memory 460 may also include software code executable by the processor 410. In certain embodiments, the communication with the networks 230 and 250 may be achieved using a single network controller.

The device 220 further includes a NAS module 470 emulating the device 220 as a NAS device and a CSS module 480 allowing the integration of the device 220 with the CSS 240. In accordance with an embodiment of the invention, the processor 410 runs an operating system (not shown) adapted to provide file-based operations on the CSS and further to control the operation of the modules 470 and 480. The storage controllers 430 include, but are not limited to, a small computer system interface (SCSI), a serial advanced technology attachment (SATA), a universal serial bus (USB), a fibre channel (FC), a serial attached SCSI (SAS), and the like. In certain embodiments, the storage devices 450 may be external to the device 220.

One of the primary tasks of the CSS module 480 is to periodically synchronize data between the device 220 (i.e., data stored in the storage devices 450) and the CSS 240. The synchronization may be in the direction from the device 220 and the CSS 240 (hereinafter “the outgoing direction”), in the direction from the CSS 240 to the device 220 (hereinafter “the incoming direction”), or simultaneously in both directions. It should be noted that all files or a partial subset of the files can be synchronized.

Synchronization in the outgoing direction is typically used as a data backup mechanism, allowing files to be backed up to the CSS 240 for safekeeping. Synchronization in the incoming direction is typically used as a data distribution mechanism, allowing files to be distributed from the CSS 240 for fast local access at the device 220 to provide fast and reliable local access to a set of files. Synchronization in both directions (bidirectional) is used to maintain data consistency between the device 220 and CSS 240. This allows to files to be modified or created both in the device 220 (through a filing sharing protocol) or the CSS 240 (through the web portal 340). It should be noted that in certain embodiments when using bidirectional synchronization one or more devices 220 can be optionally synchronized to a single location in the CSS 240. This enables multiple devices 220 to synchronize with each other through the CSS 240 which acts as a mediator.

FIG. 5 is an exemplary flowchart 500 describing the process for data synchronization implemented in accordance with an embodiment of the invention. The process will be described with a reference to a specific embodiment where the synchronization is performed in the outgoing direction. However, one of ordinary skill in the art can easily adapt the process 500 for synchronization of data in the ingoing or bidirectional directions.

At S510, files stored either in the device 220 or CSS 240 that have been changed since the last synchronization are marked. At S520, each marked file is divided into variable size blocks. At S530, each block is assigned with a unique code using, for example, a message digest code function. Thus, each block is addressed by its unique code. In accordance with an embodiment of the invention, steps S510, S520, and S530 can be executed concurrently in a pipelined fashion rather than sequentially, to provide higher efficiency.

Thereafter, it is determined which of the data blocks have been modified. With this aim, at S535, the device 220 sends the block codes of all the blocks in a file to the CSS 240, which checks whether a block with the same code exists on the scope of the same DG. If a block with the same code already exists on the CSS 240 in the same DG, then the block does not need to be transmitted. In an embodiment of the invention, the device 220 sends to the CSS 240 the block codes of all the blocks in each file. The CSS 240 then replies with a compact run length encoded (RLE) list of the blocks which are missing on the CSS and should be transferred.

The CSS 240 maintains a reference count for each block, which is increased by 1 for each file that uses this block. When a file is deleted from the CSS 240, the reference count of all the blocks of this file is reduced by 1. When the reference count of a block reaches 0, this block is no longer used by any file and the storage space of this block may be freed. It should be appreciated that this approach results in significant storage space reduction, as multiple identical files or parts of files belonging to devices in each DG are stored only once in the CSS 240. This approach also reduces the consumption of network bandwidth, as only modified blocks are transmitted over the network 250. Furthermore, the CSS 240 can store a number of previous versions for each file, allowing the user to restore a file to an earlier version. Since the file is stored as multiple blocks, the entire file does not need to be duplicated. Rather, only the differences between file versions are stored. This reduces the required storage space for file versioning.

At S540, all modified blocks that should be sent over the network 250 may be encrypted and compressed using lossless compression algorithm, to reduce the bandwidth requirements. The encryption may be a block level encryption that uses, for example, a keyed hash cryptographic message digest code function to add an authentication code to each block. In many cases the operator of the CSS is not considered a trusted party by the device owner. Thus, the encryption key can be known only to the owner of the device 220, thereby preventing even the operator of the CSS 240 from viewing or altering the contents of the stored files.

At S550 all modified blocks (optionally encrypted and compressed) are transmitted from the device 220 to the CSS 240 over the network 250. It should be noted that multiple blocks are transmitted without waiting for the CSS 240 to acknowledge the reception of a previously transmitted block, thus enabling efficient utilization of high latency links.

The communication between the device 220 and CSS 240 is performed by means of a cloud transport protocol (CTP) implemented in accordance with an embodiment of the invention. The CTP is a secure, encrypted connection based on Transmission Control Protocol (TCP)/internet protocol (IP), such as secure sockets layer (SSL) or times literary supplement (TLS). This ensures confidentiality against external eavesdroppers, or malicious modification of the data in transit. The CTP also supports a message framing protocol for sending and receiving arbitrary length messages between the device 220 and CSS 240 and implements an authentication method by which the device 220 authenticates to the CSS 240, for example, by using a security certificate (asymmetric key), or by means of a symmetric secret key or password. The CSS 240 authenticates to the device 220 by, for example, using a security certificate (asymmetric key), thus preventing an attacker from impersonating the CSS 240.

In addition to synchronizing files with the local storage available on the device 220, the CSS 240 can be utilized to expand the amount of local storage on the device 220. With this aim, the CSS 240 is exposed on the device 220 as an extended storage space in the device 220. This ability allows the device 220 to have capacities of mass storage systems (i.e., practically infinite storage space), specifically, allowing small NAS like devices to have storage space of mass storage systems. To allow access to the extended storage space as if it is on the device itself, the VCD allows read/write operations on the expanded storage space on the CSS 240.

FIG. 6 shows an exemplary and non-limiting block diagram of a cloud connector (CC) 310 implemented in accordance with an embodiment of the invention. As mentioned above one of the tasks of a cloud connector 310 is to interface between the device 220 and storage devices 320 as well as connections to cloud storage providers 330. In the current market place, there are a multitude of cloud storage service providers. However, due to a lack of a universal standard for a protocol of a cloud storage provider, most providers use proprietary interfaces and protocols. To resolve this drawback, the cloud connector 310 provides the device 220 with a unified communication protocol to access one or more cloud storage providers 330. Specifically, the cloud connector 310 acts as a gateway and translates the unified protocol, used to communicate with the device 220, to the protocols implemented by different cloud storage providers 330. It should be appreciated that this approach reduces the complexity of the device implementation, as the device 220 is not required to communicate directly with the various cloud storage providers. This approach further allows adding new cloud storage providers without modifying the device 220 or the clients 210. In addition to providing a unified interface to cloud storage providers 330, the cloud connector 310 can provide the same interface for the storage devices 320.

The cloud connector 310 includes a unified cloud protocol module 610 for communicating with the device 220 by means of the cloud transport protocol described above. The cloud connector 310 also includes a permissions-and-quotas enforcement module 620, a service entitlement database 630, a cloud cache module (CCM) 640, a storage balancing module 650, and one or more cloud protocol drivers 660 for interfacing with storage devices and cloud storage providers in the CSS 240.

The storage balancing module 650 performs load balancing between multiple cloud storage providers and possibly multiple local storage devices 330 based on criteria including, but not restricted to, performance, cost and reliability. For example, a simplistic balancing scheme could be to store 20 percent of the data to a storage device 320, and 80 percent to a cloud storage provider 330. The split between the cloud storage providers 330 can be either static (for example, according to the block code) or dynamic (for example, based on the current cost and availability of each cloud storage provider).

The CCM 640 may cache recently used or frequently accessed data blocks locally, for reduction in communication costs to the cloud storage providers and reduced latency.

The permissions-and-quota module 610 enforces and restricts devices 220 access to data blocks according to a list of access control rules. The module 610 can also enforce storage quotas for each device 220 and provide differentiated service levels per customer. The entitlement database 630 is used to store the service level agreement (SLA) for each of the customers, having accesses through clients 210, subscribed to the third party cloud storage services 330. When a customer connects the CSS 240, the entitlement database 630 is accessed to check whether the customer is entitled to the requested service. In addition, the entitlement database 630 contains additional service level information, such as storage and bandwidth quotas for each customer. It should be appreciated that the invention described herein provides a storage solution that combines the speed and practicality of NAS devices on the local network, with the scalability and disaster protection of cloud storage services.

The foregoing detailed description has set forth a few of the many forms that the invention can take. It is intended that the foregoing detailed description be understood as an illustration of selected forms that the invention can take and not as a limitation to the definition of the invention. It is only the claims, including all equivalents that are intended to define the scope of this invention.

Most preferably, the principles of the invention are implemented as any combination of hardware, firmware, and software. Moreover, the software is preferably implemented as an application program tangibly embodied on a program storage unit or computer readable medium. One of ordinary skill in the art would recognize that a “machine readable medium” is a medium capable of storing data and can be in a form of a digital circuit, an analogy circuit or combination thereof. The application program may be uploaded to, and executed by, a machine comprising any suitable architecture. Preferably, the machine is implemented on a computer platform having hardware such as one or more central processing units (“CPUs”), a memory, and input/output interfaces. The computer platform may also include an operating system and microinstruction code. The various processes and functions described herein may be either part of the microinstruction code or part of the application program, or any combination thereof, which may be executed by a CPU, whether or not such computer or processor is explicitly shown. In addition, various other peripheral units may be connected to the computer platform such as an additional data storage unit and a printing unit.

In addition, certain embodiments of the invention may be implemented in software and/or firmware are tangibly embodied on the device 220 either by the preferable means of non volatile flash memory or, less preferably, on the hard drives attached to the device. 

What is claimed is:
 1. A method for synchronizing data files between a client device and a cloud storage service (CSS), each data file being stored in the CSS as a set of at least one block that makes up the file stored in a subset of the CSS such that each block exists only once in the subset of the CSS, each block having a unique code assigned thereto in the subset of the CSS, comprising: dividing, in the client device, each data file into at least one block, the client device being associated with the subset of the CSS; assigning, in the client device, each block of the at least one block with a block code such that blocks of each data file in the client device that contain the same data as a block stored in the subset of the CSS are assigned the same code as is assigned to that same data block in the CSS; transmitting, from the client device, a list of the block codes for the blocks making up each file in the client device to the CSS; receiving at the client device from the CSS an indication of at least one block that is missing from at least the subset of the CSS; and transmitting, by the client device, each of the at least one block indicated to be missing from at least the subset of the CSS.
 2. The method of claim 1, wherein the subset of the CSS is a device group (DG).
 3. The method of claim 1, wherein the subset of the CSS is a set of blocks that are encrypted using a common block encryption key and wherein the block indicated missing from the subset of the CSS is encrypted based on the common block encryption key.
 4. The method of claim 3, wherein the encryption key is available only to an owner of the client device and is not accessible to an operator of the CSS.
 5. The method of claim 1, wherein at least two of the plurality of blocks of the subset do not correspond to a same file of the determined files.
 6. The method of claim 1, wherein at least one data file is modifiable independently at the client device and at the cloud storage service.
 7. The method of claim 1, wherein the blocks are variable size blocks.
 8. The method of claim 1, further comprising: receiving from the CSS at least an indication of at least one block that exists in the subset of the CSS but was not on the list transmitted by the client device indicating block codes that make up each file in the client device.
 9. The method of claim 1, wherein the subset of the CSS is the entirety of the CSS.
 10. The method of claim 1, wherein the at least one block indicated to be missing from at least the subset of the CSS is transmitted in a compressed format.
 11. A method for synchronizing data files between a client device and a cloud storage service (CSS), each data file being stored in the CSS as a set of at least one block that makes up the file stored in a subset of the CSS such that each block only exists once in the subset of the CSS, each block having a unique code assigned thereto in the subset of the CSS, comprising: receiving, at the CSS, a list from the client device indicating for each file of the client device to be synchronized at least one block code indicative of at least one block that makes up the file in the client device, each block of each file in the client device to be synchronized having been assigned with its block code such that blocks of a data file in the client device that contain the same data as a block stored in the subset of the CSS is assigned the same code as is assigned to that same data block in the CSS; transmitting, from the CSS, an indication of at least one block that is on the received list but is missing from at least the subset of the CSS; and receiving, by the CSS, each block indicated to be missing from the at least the subset of the CSS.
 12. The method of claim 11, wherein the subset of the CSS is a device group (DG).
 13. The method of claim 11, wherein the subset of the CSS is a set of blocks that are encrypted using a common block encryption key and wherein the block indicated missing from the subset of the CSS is encrypted based on the common block encryption key.
 14. The method of claim 13, wherein the common block encryption key is available only to an owner of the client device and is not accessible to an operator of the CSS.
 15. The method of claim 11, wherein at least two of the plurality of blocks of the subset do not correspond to a same file of the determined files.
 16. The method of claim 11, wherein at least one data file is modifiable independently at the client device and at the cloud storage service.
 17. The method of claim 11, wherein the blocks are variable size blocks.
 18. The method of claim 11, further comprising: transmitting from the CSS at least an indication of at least one block that exists in the subset of the CSS but was not on the list from the client device indicating block codes that make up each file in the client device.
 19. The method of claim 11, wherein the subset of the CSS is the entirety of the CSS.
 20. The method of claim 11, wherein the at least one block indicated to be missing from at least the subset of the CSS is in a compressed format when received. 